Connection to the Personal Geodatabase and GIS objects

Visum can temporarily connect itself with an ESRI Personal Geodatabase (PGD) or a shape file. This function can be useful for example, when a traffic modeler working with Visum, connects to a Personal Geodatabase on the computer of a land use planner. The traffic modeler can then take the required data from the Personal Geodatabase of the land use planner by means of intersection (Intersect) and then cut the connection. This process bypasses the need to import the file back to Visum.

Note: To be able to use this function, you need a license for the program ArcGIS version 8 to 10.3.

During the connection to the PGD, so-called GIS objects are created in Visum (Using Visum: GIS objects). GIS objects are POI-like network objects (Points of Interest (POI)), which are only available during a PGD connection. Analogous to POIs, GIS objects are organized into GIS categories. A GIS object is either of type point, polyline or polygon.

GIS objects have a spatial reference. This can be used for example, to illustrate the following objects in the Visum network.

  • Schools, swimming pools, stops
  • Stretches of water, agricultural areas, planning districts

To create GIS objects in Visum, you have to either select the PGD Feature Classes or Feature Datasets for display or editing. The following objects are thus created in Visum:

  • For each selected Feature Class of the Personal Geodatabase, a GIS category is created.
  • For each Feature a GIS object

None of the coordinates transferred to Visum are being converted. The GIS objects are always removed again as soon as the connection to the PGD has ended. If you want to permanently include GIS objects into the Visum network, proceed as follows:

  • Convert the GIS objects into a shape file
  • Read the GIS objects as POI for example

The following applies during the Personal Geodatabase connection:

  • Only key information on the objects is stored permanently.
  • Information on attributes of the category is available through an attribute interface.
  • Read and write access to the attributes is transferred directly to the database.